Applying custom profiles to Windows devices

A KACE Cloud custom profile references one or more existing MS Windows policies and allows you to apply it to applicable Windows devices. You can, for example, enable Location services on a target device by creating a custom profile that makes use of a Windows policy, and then applying that profile to a desired device.

Configuration of Microsoft Windows devices through MDM uses a special format language called SyncML (Synchronization Markup Language). This format language enables you to specify keys (in the form of URI’s) and values to configure the target device.

The process of referencing Windows policies is fairly technical and it assumes that you have a good understanding of the Windows Policy configuration service provider (CSP). For complete reference information, visit the Microsoft documentation found here: Configuration Service Providers. Underneath that page are additional pages that describe the various configuration service providers (CSPs) that you can use.

NOTE: While virtually all types of target device configuration are technically possible using this editor, many are not advisable. Some configurations are very complex and require extensive knowledge and experience to complete. The KACE Cloud team is working to build a simple, straight-forward mechanism, to eliminate most of the needs for a custom editor such as this one.

To better understand the process of constructing URI paths, see hands-on examples included in this section.

You can create and manage custom profiles in the Library, like other KACE Cloud configuration settings. There are two types of custom profiles: Configuration Profiles allow you to assign values to device settings and as such can be applied to devices either directly, or by adding it to an applicable KACE Cloud policy. Command Profiles can run only once on a target device, and can be directly associated to the device, but cannot be added to a policy. For details, see Add custom profiles to Windows devices.